- 
                Notifications
    You must be signed in to change notification settings 
- Fork 4.3k
ci: fix integration-test-deployment script #35716
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
bdc479e    to
    5626551      
    Compare
  
    | fetch-depth: 0 | ||
| path: head | ||
|  | ||
| - name: Configure AWS credentials | 
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can we have the OIDC? Unless there's some concern on it that i'm not aware of
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
OIDC added back in. I'm currently testing in my fork if it still works.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
| workflow_dispatch: {} | ||
| merge_group: {} | ||
| pull_request_target: | ||
| types: | 
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
What's the default behaviour if we didn't mention any?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It won't listen to any labelling events by default. So if we add the pr/needs-integration-test-deployment label, the workflow will still be skipped.
| "bump": "./bump.sh", | ||
| "build-all": "tsc -b" | ||
| "build-all": "tsc -b", | ||
| "atmosphere-integ-test": "lerna run build --scope @aws-cdk/integration-test-deployment && node tools/@aws-cdk/integration-test-deployment/bin/index.js" | 
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why is it building? I believe the normal pattern here is another separate command building, then this one only running
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
- pkglintabove in- package.jsonfollows the same pattern.
- It'll be helpful as a developer to have one command to rebuild and test the script to allow for faster development.
| Thank you for contributing! Your pull request will be updated from main and then merged automatically (do not update manually, and be sure to allow changes to be pushed to your fork). | 
| This pull request has been removed from the queue for the following reason:  The merge conditions cannot be satisfied due to failing checks:You may have to fix your CI before adding the pull request to the queue again. | 
| @Mergifyio rebase | 
- Previously, the script was executing the script under the cwd of the script package, when it should be at the head branch folder. We'll use node explicitly to run the script without changing the cwd. - Fixes the label and event conditions that would trigger the workflow. - Use STS to assume Atmosphere role as OIDC is not needed when we use the codebuild runner.
PATH environment variable is used to find yarn/node binaries. Without it, a ENOENT error is emitted when running yarn.
Running via node directly instead of lerna will keep the cwd at the root as expected.
| 
 ✅ Branch has been successfully rebased | 
b37d62c    to
    31f9616      
    Compare
  
    | Thank you for contributing! Your pull request will be updated from main and then merged automatically (do not update manually, and be sure to allow changes to be pushed to your fork). | 
| Thank you for contributing! Your pull request will be updated from main and then merged automatically (do not update manually, and be sure to allow changes to be pushed to your fork). | 
| Thank you for contributing! Your pull request will be updated from main and then merged automatically (do not update manually, and be sure to allow changes to be pushed to your fork). | 
| Comments on closed issues and PRs are hard for our team to see. | 
Reason for this change
Description of changes
Describe any new or updated permissions being added
No new permissions were added.
Description of how you validated changes
Tested on my fork here: https://github.com/Abogical/aws-cdk/actions/runs/18465794651/job/52607352315?pr=15
Checklist
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license